home *** CD-ROM | disk | FTP | other *** search
/ NetNews Offline 2 / NetNews Offline Volume 2.iso / news / comp / std / c++ / 1132 < prev    next >
Encoding:
Internet Message Format  |  1996-08-06  |  1.7 KB
  1. Path: engnews1.Eng.Sun.COM!taumet!clamage
  2. From: jcoffin@rmii.com (Jerry Coffin)
  3. Newsgroups: comp.std.c++
  4. Subject: Re: Is STL MT-Safe?
  5. Date: 17 Apr 1996 14:57:54 GMT
  6. Organization: TAEUS
  7. Approved: clamage@eng.sun.com (comp.std.c++)
  8. Message-ID: <MPLANET.31742743jcoffin989cc4@news.rmii.com>
  9. References: <4ku297$ou6@usc.edu>
  10. NNTP-Posting-Host: taumet.eng.sun.com
  11. X-Nntp-Posting-Host: slip22163.rmii.com
  12. X-Newsreader: MicroPlanet News32 v1.00 Beta Build 302
  13. Content-Length: 803
  14. X-Lines: 19
  15. Originator: clamage@taumet
  16.  
  17. In article <4ku297$ou6@usc.edu>, Hauck@mizar.usc.edu says...
  18. > Hi there,
  19. > 
  20. > I wonder if the C++ Standard Template Library (STL) is multi-thread
  21. > safe? Does anybody have experience with STL in a multi-threaded
  22. > environment?
  23.  
  24. Hmm...that's a bit like asking whether "cars are fast".  Some are, some 
  25. aren't, and of course "fast" is a bit subjective.
  26.  
  27. Likewise with STL: the classes are defined in such as way that it should be 
  28. fairly easy to make them reentrant, and they don't require the use of a lot of 
  29. global data that would have to be made thread-local.
  30.  
  31. However, that doesn't imply that every implementation of STL will be safe for 
  32. multithreaded use.  The standard says nothing about threads, so it says 
  33. equally little about the classes being safe for use with threads.
  34.     Later,
  35.     Jerry.
  36.  
  37. [ comp.std.c++ is moderated.  To submit articles: try just posting with      ]
  38. [ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu         ]
  39. [ FAQ:      http://reality.sgi.com/employees/austern_mti/std-c++/faq.html    ]
  40. [ Policy:   http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
  41. [ Comments? mailto:std-c++-request@ncar.ucar.edu                             ]
  42.